How to set keyboard focus on a module main window in a DXL

Mathias Mamsch - Tue Mar 22 05:34:40 EDT 2011

I am not sure what you mean by "Keyboard-Focus" ... You mean for example, that by "Ctrl-H" I get to edit the object heading of the current object?

Did you try:

load(moduleVersion m, true)

Maybe this helps, regards, Mathias

Mathias Mamsch, IT-QBase GmbH, Consultant for Requirement Engineering and D00RS

phenri - Tue Mar 22 09:53:34 EDT 2011
I tried your sugestion but it doesn't work.
Also I want the module to be opened in exclusive mode.

Here's what I am doing:

save (m)
downgrade (m) // Required to create a new history session number
m = edit (fullName (m), true)
setFocus (m)

The result is that when comming back from the dxl, using the arrow keys is circling through the first toolbar buttons (Save, Print, Print Preview buttons), rather then changing the current object. That means the keyboard focus is not at the right place within the module m.

I would like to have the focus on the actual current object in the module main window rather than on the toolbar.

Any idea?

phenri - Wed Mar 23 10:51:10 EDT 2011
I tried refresh(m) but still the focus is not set on the current object. The focus remains on the toolbar.
Maybe this feature is not yet available via dxl.
There is a setFocus(m) function and a setFocus(DBM) function, but there is no setFocus(m, o) function available. Maybe if I could find the DBM value of the window containing the current object I could do a setFocus(DBM) to set the keyboard focus on the current object.

phenri - Wed Mar 23 15:56:41 EDT 2011
The following dxl (simplified version) bring-up a dialog, do some housekeeping functions, and then exit the dialog.
Comming back from the dialog, the setFocus(m) gives the focus to the module's first toolbar rather than the modules's current object. If I don't do a setFocus(), a random window will get the focus, not necessarilly a DOORS windows.

DB SCR_POPUP
DBE scr
Module m = current

void closeDialog (DB win)
{
release win
} // closeDialog()

void Main (DB win)
{
// Housekeeping job according to the value of DBE scr
// ...
/ ...

save (m)
downgrade (m)
m = edit (fullName (m), true)
closeDialog (SCR_POPUP)
}

scr = field (SCR_POPUP, "Please specify PR#", "", 12, false)
apply (SCR_POPUP, "Save Module", Main)
close (SCR_POPUP, false, closeDialog)
block SCR_POPUP

setFocus (m)

Mathias Mamsch - Wed Mar 23 17:06:37 EDT 2011
I still don't get any effects, when doing DB SCR_POPUP = create "Test" in your script below, neither on DOORS 8.2 nor on DOORS 9.2.0.0. I always land at the current Object and Ctrl-H/Ctrl-T bring me into inplace-editing mode. How do you create your dialog? Any special settings (floating, etc.) and did you parent it to the module window? Do you launch it from the current module? Is it invoked from a trigger? Can anyone else reproduce the issue? Maybe it is a DOORS 9.1 only thing??

Regards, Mathias

Mathias Mamsch - Wed Mar 23 17:06:37 EDT 2011
I still don't get any effects, when doing DB SCR_POPUP = create "Test" in your script below, neither on DOORS 8.2 nor on DOORS 9.2.0.0. I always land at the current Object and Ctrl-H/Ctrl-T bring me into inplace-editing mode. How do you create your dialog? Any special settings (floating, etc.) and did you parent it to the module window? Do you launch it from the current module? Is it invoked from a trigger? Can anyone else reproduce the issue? Maybe it is a DOORS 9.1 only thing??

Regards, Mathias

llandale - Thu Mar 24 14:04:13 EDT 2011
When you first open a module, arrow keys do NOT select new objects, then work the Icons or appear to do nothing (but are preparing to select menu items). That's what's going on here.

v9.2.0.1 I indeed replicated the effect.
<1> Click on object
<2> Notice that arrow keys go to neighbor objects
<3> open and close the dialog
<4> Arrow keys now select different icons on the task bar.
<5> Some number of TABs will put the focus back on the objects and <2> works.

I tried lots of stuff. Had a little luck with "bringToFront(m)" which worked for as while, then didn't work for a while, then indeed worked for a while; but I didn't narrow down the where's and why-for's.

Getting the same behavior with "show" instead of "block".

Sorry, don't know what to do to help this. Perhaps either don't downgrade and re-edit the module, or don't worry about using the arrow keys.

• louie